Method for sharing source code over a network

ABSTRACT

Under the present invention source code can be shared among nodes in a peer-to-peer network. Specifically, source code to be shared will first be analyzed to identify a set of code patterns, assigned one or more predetermined categories based on the set of code patterns, and then selectively indexed. A developer desiring to use previously created source code when creating a new program can perform a context dependent search based on his/her working code to identify and retrieve relevant source code.

CLAIM OF PRIORITY

This continuation application claims priority to co-pending patentapplication identified by Ser. No. 10/608,204, filed on Jun. 27, 2003,entitled “Method, System and Program Product for Sharing Source CodeOver a Network”, the contents of which is hereby incorporated byreference.

CROSS-REFERENCE TO CO-PENDING APPLICATIONS

This application is related in some aspects to commonly owned U.S.patent application Ser. No. 10/295,717, filed Nov. 15, 2002, entitled“Method for Directly Providing Content and Services Via a ComputerNetwork,” and to commonly owned U.S. provisional patent application Ser.No. 60/332,651, filed Nov. 16, 2001, entitled “Method for DirectlyProviding Content and Services Via a Computer Network,” both of whichare hereby incorporated by reference.

FIELD OF THE INVENTION

The present invention generally relates to a method for sharing sourcecode over a network. Specifically, the present invention allows sourcecode to be shared, indexed and retrieved over a computer network such asa peer-to-peer network.

BACKGROUND OF THE INVENTION

As computer technology becomes more advanced, file sharing over computernetworks has become an important tool for both business and education.For example, today computer users have the capability to share data,audio and video files (i.e., in a legal fashion) with one another usingtheir own computerized devices. On particular type of network that hasgained increasing popularity for file/data sharing is a peer-to-peernetwork (commonly referred to as a P2P network). In general, apeer-to-peer networking model can be implemented in conjunction withprivate networks such as a local area network (LAN), a wide area network(WAN), a virtual private network (VPN), or with a public network such asthe Internet. In a peer-to-peer networking model, several computerized“nodes” are interconnected. Each node typically has the samecapabilities, and can initiate a communication session with anothernode. A peer-to-peer networking model can be contrasted against theclient/server or master/slave model in which the server/master hasdistinct capabilities that the clients/slaves might not have. However,in some cases, peer-to-peer communications are implemented by providingeach node both server and client capabilities. One example of a productthat supports a peer-to-peer networking model is Advanced Peer-to-PeerNetworking (APPN), which is commercially available from InternationalBusiness Machines, Corp. of Armonk, N.Y. In more recent usage,peer-to-peer networking has come to describe applications in which userscan use the Internet to exchange files with each other directly orthrough a mediating server.

One particular area in which peer-to-peer file sharing has not beenextended is for sharing source code. Specifically, when a softwaredeveloper is attempting to write new source code for a particularproduct, it can be extremely helpful to him/her to have access to thecode of previously developed products that are related to his/herproduct. Today, many software developers use an Integrated DevelopmentEnvironment (IDE) as a programming tool kit that integrates differenteditors, wizards, compilers, debuggers, and other necessary tools.Although such programming tool kits usually provide sophisticated helpsystems, as well as other resources that can assist in designing andimplementing code, modern IDEs do not support one of the most popularmethods of writing code, namely, programming by example. Although sometools exist for creating new code with design patterns and search codepatterns in an object-oriented database, such tools are based oninternal code databases. To this extent, the existing tools fall farshort of providing shared access to useful source code patterns thatwere created by individual programmers, and that are stored at multiplelocations over a network.

In view of the foregoing, there exists a need for a method, system andprogram product for sharing source code over a network. Specifically, aneed exists for a system that allows source code to be shared, indexedand retrieved in a peer-to-peer networking environment. Still yet, aneed exists for providing access to source code patterns created bymultiple developers and stored at multiple locations over a peer-to-peernetwork. A further need exists for providing efficientclassification-based navigation and content dependent searching for codepatterns from within a local IDE.

SUMMARY OF THE INVENTION

In general, the present invention provides a method, system and programproduct for sharing source code over a network. Specifically, under thepresent invention, each node in a peer-to-peer network is provided withan Integrated Development Environment (IDE), a code sharing system, anda code access/retrieval system. When a developer using a node wishes toshare code, the code sharing system on that node will be initiated.First, the source code to be shared will be analyzed in an attempt toidentify a set of code patterns. Based on the identified code patterns,one or more predetermined categories will be assigned to the sourcecode. Thereafter, code pattern information based on the code patternsand assigned categories will be stored in a centrally available codepattern directory. The source code will then be selectively indexed, anda notification about the availability of the source code will becommunicated to the other nodes in the network. If a developer usinganother node is developing new source code (i.e., “working code”), andhe/she wishes to use some previously completed, relevant source code asa reference, the code access system on the latter developer's node willbe initiated. Once initiated, the code access system will first analyzethe working code to identify a context thereof. Based on the context,one or more of the predetermined categories will be assigned to theworking code. Then, using those categories, the directory is queried anda list of categories assigned to previously developed source code thatis relevant to the working code is returned. When the developer selectsa particular category from the list, the corresponding source code isretrieved from the appropriate node. Thus, the present inventionprovides access to source code patterns that were created by multipledevelopers, and that are stored at multiple locations over apeer-to-peer network. Moreover, the present invention provides efficientclassification-based navigation and content dependent searching for codepatterns from within a local IDE.

A first aspect of the present invention provides a method for sharingsource code over a network, comprising: analyzing source code generatedon a sharing node in the network to identify a set of code patterns, andassigning at least one predetermined category to the source code basedon the identified set of code patterns; storing code pattern informationthat is based on the analysis and assignment in a directory; andselectively indexing the source code.

A second aspect of the present invention provides a system for sharingsource code over a network, comprising: a code pattern classifier foranalyzing source code generated on a sharing node in the network toidentify a set of code patterns, and for assigning at least onepredetermined category to the source code based on the identified set ofcode patterns, wherein code pattern information that is based on theanalysis and assignment is stored in a directory; and a source codeindexer for selectively indexing the source code.

A third aspect of the present invention provides a program productstored on a recordable medium for sharing source code over a network,which when executed, comprises: program code for analyzing source codegenerated on a sharing node in the network to identify a set of codepatterns, and for assigning at least one predetermined category to thesource code that is based on the identified set of code patterns,wherein code pattern information based on the analysis and assignment isstored in a directory; and program code for selectively indexing thesource code.

A fourth aspect of the present invention provides a method forselectively indexing source code for sharing over a network, comprising:recognizing at least one programming language of the source code;indexing relevant portions of the source code based on the at least oneprogramming language; recognizing and indexing a graph of source codedependencies corresponding to the source code; and recognizing andindexing a set of code types in a hierarchy associated with the sourcecode.

A fifth aspect of the present invention provides a system forselectively indexing source code for sharing over a network, comprising:a programming language recognizer for recognizing at least oneprogramming language of the source code; a selective code contentindexer for indexing relevant portions of the source code based on theat least one programming language; a dependency graph indexer forrecognizing and indexing a graph of source code dependenciescorresponding to the source code; a code type hierarchy recognizer forrecognizing a code type hierarchy associated with the source code; andan associated code type indexer for indexing a set of code types fromthe code type hierarchy that is associated with the source code.

A sixth aspect of the present invention provides a program productstored on a recordable medium for selectively indexing source code forsharing over a network, which when executed, comprises: program code forrecognizing at least one programming language of the source code;program code for indexing relevant portions of the source code based onthe at least one programming language; program code for recognizing andindexing a graph of source code dependencies corresponding to the sourcecode; program code for recognizing a code type hierarchy associated withthe source code; and program code for indexing a set of code types fromthe code type hierarchy that is associated with the source code.

A seventh aspect of the present invention provides a method foraccessing source code shared over a network, comprising: analyzingworking code on a receiving node in the network to identify a context ofthe working code, and assigning at least one predetermined category tothe working code based on the identified context; querying a directoryusing the at least one predetermined category assigned to the workingcode to identify at least one predetermined category assigned to sourcecode that is relevant to the working code; and retrieving the sourcecode from a sharing node in the network to the retrieving node based onthe at least one category assigned to the source code.

An eighth aspect of the present invention provides a system foraccessing source code shared over a network, comprising: a contextclassifier for analyzing working code on the receiving node to identifya context of the working code, and for assigning at least onepredetermined category to the working code based on the identifiedcontext; a query generator for querying a directory using the at leastone predetermined category assigned to the working code to identify atleast one predetermined category assigned to source code that isrelevant to the working code; and a code pattern requestor forretrieving the source code from a sharing node in the network to thereceiving node based on the at least one predetermined category assignedto the source code.

A ninth aspect of the present invention provides a program productstored on a recordable medium for accessing source code shared over anetwork, which when executed comprising: program code for analyzingworking code on the receiving node to identify a context of the workingcode, and for assigning at least one predetermined category to theworking code based on the identified context; program code for queryinga directory using the at least one predetermined category assigned tothe working code to identify at least one predetermined categoryassigned to source code that is relevant to the working code; andprogram code for retrieving the source code from a sharing node in thenetwork to the receiving node based on the at least one predeterminedcategory assigned to the source code.

Therefore, the present invention provides a method, system and programproduct for sharing source code over a network.

BRIEF DESCRIPTION OF THE DRAWINGS

These and other features of this invention will be more readilyunderstood from the following detailed description of the variousaspects of the invention taken in conjunction with the accompanyingdrawings in which:

FIG. 1 depicts two illustrative nodes communicating in a peer-to-peernetworking environment, according to one aspect of the presentinvention.

FIG. 2 depicts the code sharing system and code retrieval system of FIG.1 in greater detail.

FIG. 3 depicts the source code indexer of FIG. 2 in greater detail.

Is noted that the drawings of the invention are not to scale. Thedrawings are intended to depict only typical aspects of the invention,and therefore should not be considered as limiting the scope of theinvention. In the drawings, like numbering represents like elementsbetween the drawings.

BEST MODE FOR CARRYING OUT THE INVENTION

As indicated above, the present invention provides a method, system andprogram product for sharing source code over a network. Specifically,under the present invention, each node in a peer-to-peer network isprovided with an Integrated Development Environment (IDE), a codesharing system, and a code access/retrieval system. When a developerusing a node wishes to share code, the code sharing system on that nodewill be initiated. First, the source code to be shared will be analyzedin an attempt to identify a set of code patterns. Based on theidentified code patterns, one or more predetermined categories will beassigned to the source code. Thereafter, code pattern information basedon the code patterns and assigned categories will be stored in acentrally available code pattern directory. The source code will then beselectively indexed, and a notification about the availability of thesource code will be communicated to the other nodes in the network. If adeveloper using another node is developing new source code (i.e.,“working code”), and he/she wishes to use some previously completed,relevant source code as a reference, the code access system on thelatter developer's node will be initiated. Once initiated, the codeaccess system will first analyze the working code to identify a contextthereof. Based on the context, one or more of the predeterminedcategories will be assigned to the working code. Then, using thosecategories, the directory is queried and a list of categories assignedto previously developed source code that is relevant to the working codeis returned. When the developer selects a particular category from thelist, the corresponding source code is retrieved from the appropriatenode. Thus, the present invention provides access to source codepatterns that were created by multiple developers, and that are storedat multiple locations over the peer-to-peer network. Moreover, thepresent invention provides efficient classification-based navigation andcontent dependent searching for code patterns from within a local IDE.

Referring now to FIG. 1, an illustrative peer-to-peer (P2P) network 10is shown. As depicted, P2P network 10 includes node 12A (node “A”) andnode 12B (node “B”). It should be appreciated, however, that althoughtwo nodes 12A-B are depicted, P2P network 10 can actually include anyquantity of nodes. Two nodes 12A-B are shown herein for illustrativepurposes only. In any event, nodes 12A-B can be any type of computerizeddevice capable of communicating in a network environment. For example,nodes 12A-B can be a computer system such as a personal computer orlaptop, a handheld device such as a personal digital assistant or acellular telephone, etc.

As shown, nodes 12A-B generally comprise central processing units (CPUs)14A-B, memories 16A-B, buses 18A-B, input/output (I/O) interfaces 20A-B,external devices/resources 22A-B and indexes 24A-B. CPUs 14A-B maycomprise a single processing unit, or be distributed across one or moreprocessing units in one or more locations, e.g., on a client and server.Memories 16A-B may comprise any known type of data storage and/ortransmission media, including magnetic media, optical media, randomaccess memory (RAM), read-only memory (ROM), a data cache, a dataobject, etc. Moreover, similar to CPUs 14A-B, memories 16A-B may resideat a single physical location, comprising one or more types of datastorage, or be distributed across a plurality of physical systems invarious forms.

I/O interfaces 20A-B may comprise any system for exchanging informationto/from an external source. External devices/resources 22A-B maycomprise any known type of external device, including speakers, a CRT,LCD screen, hand-held device, keyboard, mouse, voice recognition system,speech output system, printer, monitor/display, facsimile, pager, etc.Buses 18A-B provides a communication link between each of the componentsin nodes 12A-B and likewise may comprise any known type of transmissionlink, including electrical, optical, wireless, etc.

Indexes 24A-B can be any systems (e.g., a databases) capable ofproviding storage for information such as selectively indexed sourcecode under the present invention. As such, indexes 24A-B could eachinclude one or more storage devices, such as a magnetic disk drive or anoptical disk drive. In another embodiment, indexes 24A-B include datadistributed across, for example, a local area network (LAN), a wide areanetwork (WAN) or a storage area network (SAN) (not shown). It shouldalso be understood that although not shown, additional components, suchas cache memory, communication systems, system software, etc., may beincorporated into nodes 12A-B.

As indicated above, nodes 12A-B typically have the same capabilities.Accordingly, memory 16A-B of each node 12A-B includes IDE 26A-B, codesharing system 28A-B and code access/retrieval system 30B. In a typicalembodiment, code sharing systems 28A-B and code access systems 30A-B areplug-ins to IDEs 26A-B. However it should be understood that this neednot be the case. Rather, code sharing systems 28A-B and code accesssystems 30A-B could be independent systems that work in conjunction withIDEs 26A-B. In addition, although nodes 12A-B in P2P network 10 areshown to each include a code sharing system 28A-B and code access system30A-B, this need not be the case either. For example, node 12A couldonly have code access system 30A, while node 12B could only have codesharing system 28B.

In any event, if a developer 38B operating node 12B wished to sharesource code with another developer over P2P network 10, he/she will doso utilizing IDE 26B and code sharing system 28B on node 12B. Similarly,if a developer 38A wished to retrieve previously completed source codeto supplement his/her working code, developer 38A will do so utilizingIDE 26A and code access system 30A on node 12A. To this extent, asreferred to herein a node that shares source code with another node isreferred to as a “sharing” node, while a node that retrieves source codefrom a sharing node is referred to as a “receiving” node.

In the following illustrative example, assume that developer 38B hasdeveloped source code that he/wishes to share with developer 38A. Aswill be further described below in conjunction with FIG. 2, when sourcecode is to be shared, developer 38B will select a button or the like inan interface of IDE 26B. This will cause code sharing system 28B toinitiate. Upon initiation, the source code will be analyzed in anattempt to identify a set (e.g., 1 or more) of code patterns. Based onthe identified code patterns one or more predetermined categories willbe assigned to the source code. In identifying code patterns, codesharing system 28B attempts to identify the type of program the sourcecode comprises. For example, source code for a web search engine wouldhave particular code patterns that identify it as a web search engine.Once the set of code patterns is identified, the source code will belabeled with one or more predetermined categories that fit the codepatterns. For example, the source code could be labeled with the “websearch engine” category. In any event, once one or more predeterminedcategories are assigned to the source code, code pattern information isstored in directory 32, which is controlled by an independent mediator(computer) system 34. Similar to indexes 24A-B, directory 32 can be anysystem (e.g., a database) capable of providing storage for informationsuch as code pattern information under the present invention. As such,directory 32 could include one or more storage devices, such as amagnetic disk drive or an optical disk drive. In another embodiment,directory 32 includes data distributed across, for example, a local areanetwork (LAN), a wide area network (WAN) or a storage area network (SAN)(not shown).

In a typical embodiment, the code pattern information stored indirectory 32 includes both the identified code patterns as well as thecategories assigned to the source code. In addition, the code patterninformation should also identify the node where the source code isstored. For example, the code pattern information could include theInternet Protocol (IP) address of node 12B. Regardless, after the codepattern information is stored in directory 32, code sharing system 28Bwill selectively index the source code, dependent code types andassociated code types. That is the relevant portions of the source code,dependent code types and associated code types will be stored in index24B. Thereafter, a notification will be sent to node 12A to informdeveloper 38A of the availability of the source code for sharing. Underthe present invention, notifications can be sent to all other nodes in aP2P network 10, or only to selected nodes.

After the source code has been selectively indexed on node 12B, it canbe access/retrieved by other developers. For example, if developer 38Awas creating new source code (i.e., working code), and he/she wished touse previously created source code as a reference, developer 38A wouldselect a button or the like in an interface of IDE 26A to initiate codeaccess system 30A. Initially, code access system 30A would analyze theworking code in a manner similar to source code. Specifically, theworking code would be analyzed to identify a context of the working codeto determine what type of program was being created. Similar to thesource code, this could involve identifying a set (e.g., one or more) ofcode patterns. Once the context is identified, one or more of thepredetermined categories would be assigned to the working code. Forexample, if the working code was for a new web search engine, thepredetermined category of “web search engine” could be assigned thereto.After one or more predetermined categories have been assigned to theworking code, code access system 30A would query the code patterninformation in directory 32 to identify source code that is relevant tothe working code. To this extent, code access system 30A will typicallygenerate and send a query to directory 32 that includes the one or morecategories assigned to the working code. These categories will be usedto find similar or like categories stored in directory 32 for previouslycreated source code. A response to the query is received by node 12A,and should list any categories that were deemed to match those assignedto the working code. That is, the response to the query will list thecategories assigned to previously created source code that are relevantto the working code (assuming relevant source code exists). Whendeveloper 38A selects a particular category in the list, the code accesssystem 30A will send a query for the corresponding source code to localsearch engine 36B of node 38B using the node identity/locationinformation (e.g., IP address) that was included in the code patterninformation for the source code. Local search engine 36B will thenretrieve the source code from index 24B and send the same back to node12A.

Referring now to FIG. 2, a more detailed description of the aboveillustrative example will be given. As indicated above, when developer38B wishes to share source code 64 he/she has created, developer 38B cando so by selecting a button or the like in an interface of IDE 26B. Thiswill cause code sharing system 28B to initiate. As shown, code sharingsystem 28B includes code pattern classifier 50, source code indexer 52and code sharing notifier 54. When code sharing system 28B is initiated,code pattern classifier 50 will first analyze source code 64 to identifya set of code patterns, and to assign one or more predeterminedcategories to the source code base on the identified code patterns. Forexample, if source code 64 is for a web search engine, code patternclassifier 50 could assign the predetermined category of “web searchengine” thereto. It should be appreciated that source code 64 couldinclude multiple code patterns. As such, source code 64 could be labeledwith multiple predetermined categories. In any event, once one or morepredetermined categories have been assigned to source code 64, codepattern information that is based on the identified set of code patternsand the assigned categories will be stored in directory 32. As indicatedabove, the code pattern information will typically include the set ofcode patterns, the categories, as well as the identity/location of“sharing” node 12B (e.g., an IP address).

After the code pattern information has been stored, source code indexer52 will selectively index the source code 64 as well as any dependentand associated code types. Referring now to FIG. 3, a more detaileddepiction of source code indexer 52 is shown. As depicted, source codeindexer 52 generally includes programming language recognizer 80,selective code content indexer 82, dependency graph recognizer 84, codetype hierarchy recognizer 86 and associated code type indexer 88. Whenselectively indexing source code 64, programming language recognizer 80will first determine the programming language (e.g., JAVA, C++, etc.) inwhich source code 64 is written. As known, IDE 26B can be used todevelop code in a number of different programming languages.Accordingly, source code 64 could be written in multiple differentprogramming languages. Programming language recognizer 80 will analyzesource code 64 and identify each such language. In one embodiment,programming language recognizer 80 could incorporate some or all of theteachings of the language translation product LINGUINI, which providesLanguage Identification for Multilingual Documents. Specifically,LINGUINI identifies the “cultural” languages (e.g., English, Spanish) indocuments. As such LINGUINI can be adapted under the present inventionto recognize different programming languages.

In any event, once the programming languages have been identified,selective code content indexer 82 will selectively index source code 64.Specifically, selective code content indexer 82 will store only therelevant portions of source code 64 in index 24B. In general, therelevant portions of source code 64 to be indexed depends upon theprogramming language thereof. For example, for a section of source code64 written in JAVA, reserved terms such as “class” and “implements” neednot be indexed. However, substantively relevant or important contentsuch as comments, type names, method names, etc. should be indexed.Selective code content indexer 82 will analyze the sections of sourcecode and index the relevant portions based on the programming languagethereof. Once source code 64 has been selectively indexed, dependencygraph recognizer 84 will identify and index the code types on whichsource code 64 depends. Specifically, as known, certain types/classes insource code 64 could depend on other types/classes. Dependency graphrecognizer 84 will consult reference source 90 to identify and indexsuch types/classes. Thereafter, code type hierarchy recognizer willidentify any hierarchies of code types/classes that are associated withsource code 64. Unlike dependent types/classes, associated types/classesare typically stored in a different location (e.g., a different file) ina hierarchy. Code type hierarchy recognizer 86 will identify any codetype/class hierarchies associated with source code 64. Once identified,associated code type indexer 88 will selectively index the codetypes/classes in the identified hierarchies. This selective indexingoccurs in a manner similar to the selective indexing of source code 64.Specifically, only the relevant portions of the associated codetypes/classes will be stored in index 24B.

Referring back FIG. 2, once source code 64 has been selectively indexed,code sharing notifier 54 will notify node 12A of the availabilitythereof. Thereafter, developer 38A is free to use source code 64 tocreate new programs. For example, assume that developer 38A is creatinga new web search engine (working code 66), and he/she wishes to usepreviously created source code as a reference. In this case, developer38A could initiate code access system 28A via an interface of IDE 26A toaccess source code 64 (or any other relevant source code). As shown,code access system 28A includes working context classifier 56, querygenerator 58, category selector 60 and code pattern requestor 62. Oncecode access system 28A has been initiated, working content classifier 56will analyze working code 66 to identify a context thereof. Inparticular, similar to code pattern classifier 50, working contentclassifier will determine the nature of working code 66 and assign oneor more predetermined categories thereto. Since developer 38A isattempting to create a new web search engine in this example, workingcode 66 could be assigned the predetermined category of “web searchengine.”

After one or more predetermined categories have been assigned to workingcode 66, query generator will generate and sent a query to directory 32.The query will at least include the categories assigned to working code66, and will be processed by directory and mediator system 34 (FIG. 1)to find code pattern information (categories) that match or correspondto the categories in the query. After the query has been processed, aresponse is returned to category selector 60 that lists anypredetermined categories assigned to previously created source code thatis relevant to working code 66. In this example, since source code 64was also assigned the predetermined category of “web search engine,”that category should be included in the list. Developer 38A is free tothen select any categories corresponding to source code he/she wishes toretrieve. Upon selecting a particular category in the list, code patternrequester 62 will retrieve the corresponding source code from theappropriate node. For example, if developer 38A selected the “web searchengine” category in the list, code pattern requester 62 would send arequest for source code 64 to local search engine 36B, which wouldretrieve source code from index 24B and return the same to node 12A.Once received, developer 38A can use portions or all of source code 64in his/her working code 66.

It should be understood that the present invention can be realized inhardware, software, or a combination of hardware and software. Any kindof computer/server system(s)—or other apparatus adapted for carrying outthe methods described herein—is suited. A typical combination ofhardware and software could be a general purpose computer system with acomputer program that, when loaded and executed, carries out therespective methods described herein. Alternatively, a specific usecomputer, containing specialized hardware for carrying out one or moreof the functional tasks of the invention, could be utilized. The presentinvention can also be embedded in a computer program product, whichcomprises all the respective features enabling the implementation of themethods described herein, and which—when loaded in a computer system—isable to carry out these methods. Computer program, software program,program, or software, in the present context mean any expression, in anylanguage, code or notation, of a set of instructions intended to cause asystem having an information processing capability to perform aparticular function either directly or after either or both of thefollowing: (a) conversion to another language, code or notation; and/or(b) reproduction in a different material form.

The foregoing description of the preferred embodiments of this inventionhas been presented for purposes of illustration and description. It isnot intended to be exhaustive or to limit the invention to the preciseform disclosed, and obviously, many modifications and variations arepossible. Such modifications and variations that may be apparent to aperson skilled in the art are intended to be included within the scopeof this invention as defined by the accompanying claims. For example,although the illustrative example discussed herein involved node 12Bbeing the “sharing” node and node 12A being the “receiving” node, anypossible combination of roles is possible.

1. A method for accessing source code shared over a network, comprisingat least one computing device for processing the steps of: providing thenetwork with an Integrated Development Environment (IDE) which includesclassification-based navigation and content dependent searching for codepatterns; analyzing working code on a receiving node in the network toidentify a context of the working code, and assigning at least onepredetermined category to the working code based on the identifiedcontext, wherein the categories include comments, type names and methodnames; querying a directory using the at least one predeterminedcategory assigned to the working code to identify at least onepredetermined category assigned to source code that at least one ofmatches or corresponds to the category assigned to the working code;returning a list of categories; selecting at least one category from thelist of categories; retrieving the source code from a sharing node inthe network to the retrieving node based on the at least one categoryselected from the list of categories, wherein the retrieving comprisesquerying a search engine corresponding to the sharing node to retrievethe source code; analyzing the source code on the sharing node toidentify a set of code patterns, and assigning the at least onepredetermined category to the source code based on the identified set ofcode patterns; storing code pattern information that is based on theanalysis and assignment in a directory; and selectively indexing thesource code, prior to analyzing the working code, wherein the indexingcomprises: recognizing at least one programming language of the sourcecode; analyzing sections of the source code; indexing relevant portionsof the source code based on the at least one programming language,wherein the relevant portions include comments, type names and methodnames; recognizing and indexing at least one source code dependencycorresponding to the source code; and recognizing a set of code typehierarchies associated with the source code; and indexing the code typesin the recognized set of code type hierarchies; notifying a set of othernodes in the network of the availability of the source code.
 2. Themethod of claim 1, wherein the retrieving step comprises retrieving thesource code from the sharing node to the retrieving node upon selectionof the at least one category selected from the list of categoriesassigned.
 3. The method of claim 1, wherein the retrieving stepcomprises querying a search engine corresponding to the sharing node toretrieve the source code.
 4. The method of claim 1, further comprisingnotifying a set of other nodes in the network of the availability of thesource code.
 5. The method of claim 1, wherein the network is apeer-to-peer network.